OpenText Cordys 10.6 documentation : Independent Subprocess Properties Interface

Independent Subprocess Properties Interface
This topic describes the fields on the Sub-process Properties pane.


Table 1. Fields on the General Tab

Field Description
Description A description of the sub-process.
Font Size Allows the user to decrease or increase the font size of the text within the activity. The default font size is 12.
Sub Process

Select Static Value or Read From Message value to the independent sub-process.The Independent Sub-process to be executed is read from the message that is defined in the Read From Message field. When you select Read From Message, set the XPath of the message containing the sub-process name.

Note: If you selected the Read From Message option, ensure to provide the exact path of the sub-process. If you typed the name of the sub-process or do not provide the exact path, the sub-process will not be invoked if it is created within a folder in the CWS project. Only the sub-processes that are not created within a folder will be invoked in such scenarios. Alternatively, use the Static Value option and select the appropriate process name from the list that is displayed.
Instance ID

The process model is instantiated with the defined identifier only if this field includes the defined identifier in the XPath of the message. Also, ensure that the defined identifier is unique.
Instantiation Source Select Same as Main Process to display the instantiation source for the linked business process or select Other to indicate that the instantiation source for the linked business process is not the same as its main process.
Execution Priority

Select one the following options to set an execution priority for the linked business process:

  • Same as Main Process - Priority is same as defined in the main process.
  • Same as Sub Process - Priority is same as defined in the linked business process.
  • Other - To specify the execution priority that is different to the main process and the subprocess, select one of the following:
    • Static - You can select any one of the priority levels: Highest, High, Normal, Low, and Lowest.
    • Read from message - If you want to dynamically set the execution priority.

      Note: If the Read from Message is selected and an invalid value is provided, then the priority of the parent process will be considered; value will be considered invalid, if it is either empty, non-numeric, or contains a value less than 1 or greater than 5.
Wait until Sub Process is Finished If you select this check box, the main process will wait till the sub-process sends the expected output message or indicates that the next activity in the main process can start processing. If you clear this check box, the main process will start the sub-process and continue with the next activity. The main process can synchronize with the sub-process by receiving a message through the Receive Message event. In the sub-process, a Send Message Activity or end Event can send this message or communication to the main process.
Note: This option is disabled if the sub-process is a short-lived process.
Execute Condition

The Execute Condition can be of types - None, Static Value or Read From Message. Select the Static Value option to specify the actual condition for execution.Select the Read From Message option to read the condition from the XPath of the message. You can build a condition by clicking the XPath editor icon ( ) appearing at the end of this field.
Note:

  • Ensure that the Read From Message condition which is taken from the Message Map does not start with a slash.
  • If a message contains an XPath expression, then the XPath need not be in single quotes. For example, if the message is /mycondition and it contains an expression as follows: GetEmployeeOutput/GetEmployeeResponse/tuple/old/Employees/City = "London".
  • If the specified execute condition is satisfied, the activity is executed otherwise, it is skipped.
    In a sub-process construct, the Execute Condition option can be used instead of the Decision construct. Thus, you do not need to explicitly model a decision construct when only one path from the Decision construct leads to an activity.You can view the decision icon on the left bottom corner of the construct indicating that the activity includes a condition for execution.
Execution User Type Select the Current User or Process Instantiation User for the selected activity.For each instance of a process, there can be either a Current User or a Process Instantiation User. The Process Instantiation User can trigger the process while the Current User is the one who is currently logged on.



Table 2. Fields on the Messages Tab

Field Description
Share Message Map

 

Allows user to share the Message Map of the main process with the sub-process.
Note:

  1. This feature is currently deprecated. It is available only if the business processes were migrated using this option in the earlier versions of the product. We recommend our users to use 'Send Message' and 'Receive Message' Intermediate Events to pass data between the processes.
  2. If the Share Message Map option is selected then the Wait until Sub Process is Finished option is disabled and the main process remains in waiting state until the sub-process is finished. Also, the Execution User Type is assigned to Current User.
  3. If the Share Message Map option is selected, then the user does not have to define an input or output message; the entire Message Map is shared with the Independent Sub-process.
Input Message Refers to the input message for the Independent Sub-process to start. Drag the required input message from the project content tree in Workspace Documents (Explorer) view. Click and select the required message from the Select a Message window that appears. The Select a Message window displays all process specific messages, Web service message and Independent Sub-process messages that are available for the current business process model.
Note: You can also Add Document or Add Runtime Reference from the Select a Message window.
Output Message Refers to the output message shown after the Independent Sub-process is complete. Drag the required output message from the project content tree in Workspace Documents (Explorer) view . Click and from the Select a Message window, select required message . The Select a Message window displays all process specific messages, Web service message and Independent Sub-process messages that are available for the current business process model.
Note: You may also Add Document or Add Runtime Reference from the Select a Message window.



Table 3. Fields on the Monitoring Tab

Field Description
Configure Monitoring on Spatial Level Enable/disable monitoring for the Independent Sub-process activity. By default, the options defined in the Default Activity Monitoring tab at process level are inherited by the newly created activity.
Monitor Level


Refers to the level of monitoring that you want to set on the Independent Sub-Process activity.

  • Activity status: Records activity status, timestamp, and user information.
  • Activity status, input and output messages: Records the input and output messages of the activity along with its status.
  • Store complete activity information when activity aborts: Records activity status and input and output messages information only when the process aborts. If the activity is successfully completed, none of the monitoring information is recorded.

    Note: Monitoring options at activity level are dependent upon the options defined at process level in the Default Activity Monitoring tab. You can override the monitoring activity and store the relevant recovery point settings to each individual activity level, by clicking the Apply Default Settings button.
Monitoring on Sub Process Level > Monitoring Option Select As Defined in Sub Process to monitor the sub-process instance as defined in the independent sub-process itself or select Specific to this Process to specify custom monitoring options for that activity in the main process.
Note: If you change the Monitoring settings of the sub-process activity in the main process, these settings will be applied to the sub-process instance and will override the settings defined on the sub-process.
Monitoring on Sub Process Level > Monitoring Level

Select required Monitoring Level from the drop-down list:

  • Process status: Records basic information of a process such as status, timestamp, user information, and so on.
  • Process input and output messages: Records basic information of a process as well as input and output messages of the business process.
  • Process status, input, output messages and message- map: Records basic information of a process, input and output messages, and message map of the business process.
  • Store complete process information when process aborts: Records basic information of a process always. Records input and output messages, and message map of a business process only if the process aborts.



Table 4. Fields on the Annotation Tab

Field Description
Annotation Additional notes or comments on the independent sub-process, if any.

Related tasks

Setting the Properties of an Independent Subprocess